TrackGPS by AROBS
TrackGPS by AROBS
Confidential - For Discussion Purposes Only
01 / 14
Asset Recovery Proposal

Asset Recovery Proposal for Coca-Cola Global Equipment Platform

Device options, data architecture, and pilot path for global equipment recovery, presented with a transparent commercial and technical view for board-level evaluation.

Prepared By TrackGPS by AROBS
Format Technical + Commercial Proposal
Date June 2026
01
Recovery-First Scope
The proposal is centered on equipment recovery, location visibility, battery life, and low-touch field operations.
02
Transparent Option Comparison
Each solution will be presented on the same structure, with consistent pricing logic.
03
Pilot-to-Scale View
The presentation is designed to support a 100-unit pilot decision while showing clear indicative pricing at 1,000 and 10,000 units.
(c) 2026 TrackGPS by AROBS Board Proposal Draft
Coca-Cola Global Equipment Platform
TrackGPS by AROBS
TrackGPS by AROBS
Confidential - For Discussion Purposes Only
02 / 14
Executive Summary

Focused on equipment recovery with a transparent option review path

This proposal addresses the immediate recovery use case first, with a structured comparison of up to four device options against the operating requirements that matter most for Coca-Cola and its bottlers.

Business Need

Phase 1 is location recovery, not full telemetry.

The immediate decision is where equipment is, when it moved, and how to support low-touch operations with long battery life.

Priority criteria: location visibility, battery endurance, easy installation, open data model
Options Reviewed
Up to four device options can be evaluated under the same presentation structure.
Each option is shown with the same technical, operational, and commercial checkpoints.
Indicative pricing will be shown consistently at 100, 1,000, and 10,000 units.
Evaluation Approach
Each solution is assessed on form factor, connectivity, battery estimate, data flow, timeline, and cost.
The comparison is designed to make trade-offs visible before a preferred direction is selected.
Decision Path
This presentation aligns stakeholders on the evaluation path before final option selection.
A 100-unit pilot remains the next logical step once the preferred path is agreed.
Future telemetry remains a later expansion after recovery fit is proven.
(c) 2026 TrackGPS by AROBS Executive Summary
Evaluation path before preferred option selection
TrackGPS by AROBS
TrackGPS by AROBS
Confidential - For Discussion Purposes Only
03 / 14
Business Need

Recovery visibility first. Operational simplicity must follow.

The immediate business need is to recover missing equipment faster, understand movement with less manual effort, and support a deployment model that can work across bottlers at scale.

The Current Problem

Equipment can move out of place without enough recovery visibility.

The practical question is simple: where is the asset now, and when or where did it move from its expected location.

Why It Matters

This is bottler capital with direct operational impact.

Recovery delays affect asset control, replacement cost, and field efficiency. The value of the first phase is better recovery, not full telemetry.

What Success Looks Like
Reliable visibility into where equipment is and when movement occurs.
Long battery life with minimal service burden in the field.
Portable data that can be shared cleanly across Coca-Cola and bottler systems.
What The Solution Must Deliver
Small form factor and low-touch installation.
Low cost at scale with clear pricing structure.
Open and portable data architecture.
No Bluetooth or WiFi dependence in the core operating model.
Phase 1 focus: location visibility, movement awareness, battery endurance, scalable deployment
(c) 2026 TrackGPS by AROBS Business Need
Recovery-first scope for the initial decision
TrackGPS by AROBS
TrackGPS by AROBS
Confidential - For Discussion Purposes Only
04 / 14
TrackGPS Footprint

Relevant scale, real deployments, and operational credibility

Before selecting a device path, the board should also see the operating base behind the proposal: active deployments, enterprise adoption, and a platform already used at scale.

20+
Years of industrial expertise
9,700+
Enterprise clients worldwide
150K+
Active assets tracked daily
99.9%
Mission-critical uptime SLA
Why This Matters

The proposal is backed by an existing operating platform, not a greenfield concept.

The value for Coca-Cola is not only the device selection itself, but the ability to connect that device into a proven asset-tracking environment with established service and support discipline.

Heat map and market footprint visual can be added in the next iteration
What This Demonstrates
TrackGPS already operates at enterprise scale with daily monitored assets.
The proposal is grounded in deployment experience, not only in hardware evaluation.
The same platform logic can support recovery-first rollouts and later expansion.
(c) 2026 TrackGPS by AROBS TrackGPS Footprint
Existing scale behind the proposed solution path
TrackGPS by AROBS
TrackGPS by AROBS
Confidential - For Discussion Purposes Only
05 / 14
Processing Architecture

Processing backbone and downstream delivery flow

High-level infrastructure view: ingest, route, process, and deliver asset data.

TrackGPS high-level IoT Hub processing diagram
(c) 2026 TrackGPS by AROBS Processing Architecture
Ingestion, ordering, event routing, and service distribution
TrackGPS by AROBS
TrackGPS by AROBS
Confidential - For Discussion Purposes Only
06 / 14
Integration & Open Data

From device message to portable enterprise data delivery

Beyond device connectivity, TrackGPS provides the integration layer required to receive, normalize, decode, and deliver data into client and bottler-side systems through established enterprise interfaces.

Tracked Asset Recovery device sends event and status data
→
Connectivity & HUB Ordered ingestion, acknowledgement, message control
→
TrackGPS IoT Processing Decode, normalize, enrich, route, persist
→
Client Delivery Layer Open outputs for enterprise integration and downstream use

Core Backend Stack

.NET Full Framework supports the current ingestion and processing layer used for operational delivery.

Open Delivery Methods

Existing integration methods include FTP, Kafka, JSON-based delivery, and SOAP-based system connectivity.

Portable Data Model

Data can be structured for export and reuse, supporting portable integration into Coca-Cola and bottler-side environments.

Integrator Positioning

TrackGPS sits at the orchestration layer between device-originated data and client-specific enterprise consumption paths.